UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The print-category variable for the configuration of BIND 9.x server logs must be configured to record information indicating which process generated the events.


Overview

Finding ID Version Rule ID IA Controls Severity
V-72389 BIND-9X-001032 SV-87013r1_rule Low
Description
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. Associating information about where the event occurred within the application provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured application. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality.
STIG Date
BIND 9.x Security Technical Implementation Guide 2018-01-02

Details

Check Text ( C-72593r1_chk )
For each logging channel that is defined, verify that the "print-category" sub statement is listed.

Inspect the "named.conf" file for the following:

logging {
channel channel_name {
print-category yes;
};
};

If the "print-category" statement is missing, this is a finding.

If the "print-category" statement is not set to "yes", this is a finding.
Fix Text (F-78745r1_fix)
Edit the "named.conf" file.

Add the "print-category" sub statement to the "channel" statement.

Configure the "print-category" sub statement to "yes"

Restart the BIND 9.x process.